Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

versions: Bump fedora base image versions #1860

Conversation

stevenhorsman
Copy link
Member

  • Fedora 38 has passed EoL 3 weeks ago, so we should try and bump to the next version (or possibly even 40?).
  • Once golang-fedora:1.21.11-39 is built, this will be followed up with a bump of the builder_base we use as well,
    but do to the chance of breaking things I'll keep it separate for now.

- Fedora 38 has passed EoL 3 weeks ago, so we should try and bump to the
next version (or possibly even 40?).
- Once `golang-fedora:1.21.11-39` is built, this will be followed up with
a bump of the builder_base we use as well,
but do to the chance of breaking things I'll keep it separate for now.

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
@wainersm
Copy link
Member

Hi @stevenhorsman !

  • Fedora 38 has passed EoL 3 weeks ago, so we should try and bump to the next version (or possibly even 40?).

I'm glad that you noticed that this time. But I was wondering how we could automatically detect distros reaching EOL and act on. I've found this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan gh action that leverages this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan tool. I liked both action and tool, I believe it can help on solving our problem. Worth an issue to track that idea?

Other than that, I check that mkosi based Fedora podvm is already on 39 (great!):

src/cloud-api-adaptor/podvm-mkosi/mkosi.presets/system/mkosi.conf.d/fedora.conf

* Once `golang-fedora:1.21.11-39` is built, this will be followed up with a bump of the builder_base we use as well,
  but do to the chance of breaking things I'll keep it separate for now.

It won't make sense to run the libvirt CI as caa binary will be still built on 38 and attempted to run on 39. right?

Copy link
Member

@wainersm wainersm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stevenhorsman !

Copy link

@huoqifeng huoqifeng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks @stevenhorsman

@stevenhorsman stevenhorsman merged commit e98b450 into confidential-containers:main Jun 13, 2024
18 checks passed
@stevenhorsman
Copy link
Member Author

But I was wondering how we could automatically detect distros reaching EOL and act on. I've found this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan gh action that leverages this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan tool. I liked both action and tool, I believe it can help on solving our problem. Worth an issue to track that idea?

Definitely worth an issue to track this. Thanks for the suggestion!

@stevenhorsman stevenhorsman deleted the bump-base-image-to-fedora-39 branch October 3, 2024 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants